-
Notifications
You must be signed in to change notification settings - Fork 665
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flyte-core add missing podEnv values #4807
Flyte-core add missing podEnv values #4807
Conversation
- In flyteorg#4756 / fb9ffd5, flyte-core got consistent podEnv values established in values.yaml. However, these values were not properly injected into *all* the containers being used in various deployments. Fix that so that they are used in all deployments Signed-off-by: ddl-ebrown <[email protected]>
- Some linters consider empty env: as invalid k8s YAML, because env is typically an [] when no values are set Prevent rendering the console env block without values Signed-off-by: ddl-ebrown <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4807 +/- ##
==========================================
+ Coverage 58.98% 59.12% +0.14%
==========================================
Files 644 644
Lines 55145 52788 -2357
==========================================
- Hits 32527 31213 -1314
+ Misses 20046 19001 -1045
- Partials 2572 2574 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So did you find this out by deploying with podEnvs correct?
Thanks!
Correct. We have some checks in our deployments that set |
@ddl-ebrown for the failing check, you should rebase onto |
In Fix webhook typo, add podLabels, add podEnv to flyte-core Helm chart #4756 / fb9ffd5, flyte-core got
consistent podEnv values established in values.yaml. However, these
values were not properly injected into all the containers being
used in various deployments.
Fix that so that they are used in all deployments
Make sure console doesn't render an empty env: block
Tracking issue
https://github.com/flyteorg/flyte/issues/
Why are the changes needed?
What changes were proposed in this pull request?
How was this patch tested?
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link